Recurring opinions or productive improvements—what agile teams actually discuss in retrospectives
نویسندگان
چکیده
منابع مشابه
Evidence-Based Timelines for Agile Project Retrospectives - A Method Proposal
Retrospective analysis of agile projects can support identification of issues through team reflection and may enable learning and process improvements. Basing retrospectives primarily on experiences poses a risk of memory bias as people may remember events differently, which can lead to incorrect conclusions. This bias is enhanced in project retrospectives which cover a longer period compared t...
متن کاملAgile Experience: Communication and Collaboration in Agile Software Development Teams
Introduction This research explored aspects of agile development teamwork initiatives associated with positive socio-psychological phenomena, with a focus on phenomena outside the scope of traditional management, organizational, and software engineering research. The motivation for this research was to better explore the animation and excitement observed in practitioners of agile software devel...
متن کاملSix Sigma for Agile Teams
Purpose – This paper addresses the most common pain points in agile software development. Methodology/Approach – Many experts agree that agile software development methodologies make good use of best practices – but how can they be measured quantitatively? Agile literature provides surprises for software measurement professionals: for instance, time-consuming size measurement approaches are pro...
متن کاملSupporting Self-Organizing Agile Teams
Self-organizing Agile teams need a supportive environment to emerge and flourish. Through a Grounded Theory study of 58 Agile practitioners across 23 different software organizations in New Zealand and India, we found that senior management support is a critical environmental factor influencing selforganizing Agile teams. We describe the influence of senior management, and show how their suppor...
متن کاملKnowledge Sharing in Agile Software Teams
Traditionally, software development teams follow Tayloristic approaches favoring division of labor and, hence, the use of role-based teams. Role-based teams require the transfer of knowledge from one stage of the development process to the next. As multiple stages are involved, the problem of miscommunication due to indirect and long communication path is amplified. Agile development teams addr...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
ژورنال
عنوان ژورنال: Empirical Software Engineering
سال: 2016
ISSN: 1382-3256,1573-7616
DOI: 10.1007/s10664-016-9464-2